error1002bigbluebutton

1002:CouldnotmakeaWebSocketconnection-TheinitialWebSocketconnectionwasunsuccessful.PossibleCauses:Firewallblockingwsprotocol;Serverisdown ...,2020年9月10日—Restartthemachine(AdjusttheconfigurationoftheGCPmachine,butthepubliciphasnotchanged),a1002errorappears,microphoneisnot ...,2021年3月2日—RAM:16GB.Additionalcontextbbb-conf--check:`BigBlueButtonServer2.2.33(2347)Kernelversion:4.4.0-203 ...,20...

參考資訊如下
Troubleshooting Guide

1002: Could not make a WebSocket connection - The initial WebSocket connection was unsuccessful. Possible Causes: Firewall blocking ws protocol; Server is down ...

could not make a WebSocket connection (Error 1002) ...

2020年9月10日 — Restart the machine (Adjust the configuration of the GCP machine, but the public ip has not changed), a 1002 error appears, microphone is not ...

WebSocket Connection Error

2021年3月2日 — RAM: 16GB. Additional context bbb-conf --check: `BigBlueButton Server 2.2.33 (2347) Kernel version: 4.4.0-203 ...

Could not make a WebSocket connection (error 1002) #398

2021年7月17日 — Hi, I installed bigbluebutton on my server an all seems to be well after a long struggle but when I start a session either using the moodle ...

Error 1002 Chrome · Issue #13900 · bigbluebutton ...

2021年12月11日 — When i try start audio with mic i get error 1002. Steps to reproduce the behavior: start room; i get popup with the message Connecting and ...

Error 1002, could not connect to websocket on fresh install

2020年12月28日 — I ran wget -qO- https://ubuntu.bigbluebutton.org/bbb-install.sh | bash -s -- -w -a -v xenial-22 -s bbb.example.com -e [email protected] replacing ...

WebRTC issue: Error 1002

2022年5月16日 — I have a working BBB server. Upon creating a clone of this server through snapshot using AWS EC2, I am facing this issue on the clone.

1002

The 1002 error is caused when the BigBlueButton client (or more specifically your browser) can not make a websocket connection to your BigBlueButton server.

WebRTC issue

As the docs say, it's very likely a configuration issue on the server (did you upgrade to HTTPS) or you have a firewall that is preventing the websocket ...